Approval Fails When There Is a Comma in a Map's File Path

Symptoms

A map is approved through the Approvals webpage, but the approval status and date are not set in the map.

Cause

Approval can fail if there is a comma in the map's file path. This could be in the map's file name or in one of the folders in that path.

When a map is approved, Approval properties are updated through a 'silent' or 'mini' publish, which runs REPLACEDATA tasks on a set of maps defined by a comma-delimited list. If there is a comma in a map's path, it confuses that mechanism.

Evidence can be found in the Silent Publish logs.

Triaster\TriasterServer2011\Logs\SilentPublish\PublicationLog <Library> <Site> <Date> <Time>.xml

where records of this form would be expected:

<LogEntry TimeLogged="17/11/2014 13:29:25"

Type="Info" ServerName="MyServer"><

Task Type="REPLACEDATA" ShapeType="Node" PropertyName="contentapprovaldate"

SearchFor="" ReplaceWith="17/11/2014" MatchCase="FALSE" ForceCreate="TRUE"

Category="Write"

Nodes="e:\triaster\triasterserver2011\mapstore\process library\prelive maps\this, that and the other\mymap 1.vdx!{e755f246-3b49-42c3-afb7-8f2d435fc60e},

e:\triaster\triasterserver2011\mapstore\process library\prelive maps\this, that and the other\mymap 2.vdx!{7f112fd9-e4b9-4fd4-b0f9-626c1c610afe}" />

</LogEntry>

In this example, the commas in the folder name would conflict with the commas used to delimit the map identities.

Solution

Commas should not be used in folder or file names. If commas are removed from such names, then the links from other maps to those files will also need to be amended. Links from maps where the source and target are both within such folders should be relative, and not contain explicit references to such a folder, so should remain valid. Links that navigate in or out of such folders will need to be changed.